Memory controller utilizing an error coding dispersal function

ABSTRACT

A computing core includes memory and a memory controller. The memory is partitioned into a user section and a kernel section. The user section is divided into a first set of pillars and the kernel section is divided into a second set of pillars. The memory controller is operable to dispersed storage error encode a data segment of user data into a set of encoded user data slices. The memory controller is further operable to store the set of encoded user data slices in the first set of pillars of the user section. The memory controller is further operable to dispersed storage error encode a data segment of system data into a set of encoded system data slices. The memory controller is further operable to store the set of encoded system data slices in the second set of pillars of the kernel section.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility patent application claims priority pursuant to35 U.S.C. §120 as a continuation of U.S. Utility application Ser. No.14/014,692, entitled “MEMORY CONTROLLER UTILIZING AN ERROR CODINGDISPERSAL FUNCTION”, filed Aug. 30, 2013, issuing as U.S. Pat. No.9,405,607, on Aug. 2, 2016, which is a continuation of U.S. Utilityapplication Ser. No. 12/755,232, entitled “MEMORY CONTROLLER UTILIZINGAN ERROR CODING DISPERSAL FUNCTION”, filed Apr. 6, 2010, which claimspriority pursuant to 35 U.S.C. §119(e) to U.S. Provisional ApplicationNo. 61/230,304, entitled “COMPUTING SYSTEM UTILIZING DISPERSED STORAGE”,filed Jul. 31, 2009, all of which are hereby incorporated herein byreference in their entirety and made part of the present U.S. Utilitypatent application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not Applicable

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not Applicable

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates generally to computing systems and moreparticularly to data storage solutions within such computing systems.

2. Description of Related Art

Computing systems are known to communicate, process, and store data.Such computing systems range from wireless smart phones to data centersthat support millions of web searches, stock trades, or on-linepurchases every day. Computing processing is known to manipulate datafrom one form into another. For instance, raw picture data from an imagesensor may be compressed and/or manipulated in accordance with a picturecompression standard to produce a standardized compressed picture thatcan be saved or shared with others.

With continued advances in computing processing speed and communicationspeed, computers manipulate real time media from voice to streaming highdefinition video. As such, general-purpose information appliances arereplacing purpose-built communications devices (e.g., a telephone). Forexample, smart phones can support telephony communications but they arealso capable of text messaging and accessing the internet to performfunctions including email, web browsing, remote applications access, andmedia communications (e.g., telephony voice, image transfer, musicfiles, video files, real time video streaming. etc.).

Each type of computing system is constructed, and hence operates, inaccordance with one or more communication, processing, and storagestandards. As a result of standardization and with advances intechnology, more and more information content is being converted intodigital formats. For example, more digital cameras are now being soldthan film cameras, thus producing more digital pictures. As anotherexample, web-based programming is becoming an alternative to over theair television broadcasts and/or cable broadcasts. As further examples,papers, books, video entertainment, home video, etc. are now beingstored digitally, which increases the demand on the storage function ofcomputing systems.

A typical computer storage function includes one or more memory devicesaligned with the needs of the various operational aspects of thecomputer system's processing and communication functions. Generally, theimmediacy of access dictates what type of memory device is used. Forexample, random access memory (RAM) memory can be accessed in any randomorder with a constant response time, thus it is typically used for cachememory and main memory. By contrast, memory device technologies thatrequire physical movement such as magnetic disks, tapes, and opticaldiscs, have a variable response time as the physical movement can takelonger than the data transfer, thus are typically used for secondarymemory (e.g., hard drive, backup memory, etc.).

Computer system storage standards include, but are not limited to,network file system (NFS), flash file system (FFS), disk file system(DFS), small computer system interface (SCSI), internet small computersystem interface (iSCSI), file transfer protocol (FTP), and web-baseddistributed authoring and versioning (WebDAV). Such standards specifythe data storage format (e.g., files, data objects, data blocks,directories, etc.) and interface between the computer system'sprocessing function and the memory devices. Typically a memorycontroller provides the interface function between the processingfunction and the memory devices and will have to change as new storagesystems are developed.

Despite the standardization of the computer system and its memory,memory devices fail; especially commercial grade memory devices thatutilize technologies incorporating physical movement (e.g., a discdrive). For example, it is fairly common for a disc drive to routinelysuffer from bit level corruption and to completely fail after threeyears of use. One solution is to utilize a higher-grade disc drive,which adds significant cost to the computing system.

Another solution is to utilize multiple levels of redundant disc drivesto replicate the data into two or more copies. One such redundant driveapproach is called redundant array of independent discs (RAID). In aRAID device, a RAID controller adds parity data to the original databefore storing it across the array. The parity data is calculated fromthe original data such that the failure of one or more discs will notresult in the loss of the original data. For example, RAID 5 uses threediscs to protect data from the failure of a single disc. The paritydata, and associated redundancy overhead data, reduces the storagecapacity of three independent discs by one third (e.g., n−1=capacity).RAID 6 can recover from a loss of two discs and requires a minimum offour discs with a storage capacity of n−2.

While RAID addresses the memory device failure issue, it is not withoutits own failure issues that affect its effectiveness, efficiency andsecurity. For instance, as more discs are added to the array, theprobability of a disc failure increases, which increases the demand formaintenance. For example, when a disc fails, it needs to be manuallyreplaced before another disc fails and the data stored in the RAIDdevice is lost. To reduce the risk of data loss, data on a RAID deviceis typically copied on to one or more other RAID devices. While thisaddresses the loss of data issue, it raises a security issue sincemultiple copies of data are available, which increases the chances ofunauthorized access. Further, as the amount of data being stored grows,the overhead of RAID devices becomes a non-trivial efficiency issue.

Therefore, a need exists for a data storage solution that provides morereliable storage of data, minimizes adverse affects of multiple memoryelements failures, provides improved security, is adaptable to a widevariety of storage system standards, and/or is compatible with computingand communications systems.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a computingsystem in accordance with the invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing corein accordance with the invention;

FIG. 3 is a schematic block diagram of an embodiment of a dispersedstorage processing module in accordance with the invention;

FIG. 4 is a schematic block diagram of another embodiment of a dispersedstorage processing unit in accordance with the invention;

FIG. 5 is a schematic block diagram of another embodiment of a dispersedstorage processing unit in accordance with the invention;

FIG. 6 is a schematic block diagram of an embodiment of a grid module inaccordance with the invention;

FIG. 7 is a diagram of an example embodiment of error coded data slicecreation in accordance with the invention;

FIG. 8 is a schematic block diagram of an embodiment of a memory mappingin accordance with the invention;

FIG. 9 is a schematic block diagram of an embodiment of a memorycontroller in accordance with the invention;

FIG. 10 is a logic diagram of an embodiment of a method for datahandling in accordance with the present invention;

FIG. 11 is a schematic block diagram of another embodiment of a memorycontroller in accordance with the invention;

FIG. 12 is a schematic block diagram of another embodiment of a memorycontroller in accordance with the invention;

FIG. 13 is a schematic block diagram of another embodiment of acomputing core in accordance with the invention;

FIG. 14 is a logic diagram of another embodiment of a method for datahandling in accordance with the present invention;

FIG. 15 is a schematic block diagram of another embodiment of a memorymapping in accordance with the invention;

FIG. 16 is a schematic block diagram of another embodiment of a memorymapping in accordance with the invention;

FIG. 17 is a logic diagram of an embodiment of a method for BIOSalerting in accordance with the present invention;

FIG. 18 is a schematic block diagram of another embodiment of a memorymapping in accordance with the invention;

FIG. 19 is a schematic block diagram of another embodiment of a memorymapping in accordance with the invention;

FIG. 20 is a schematic block diagram of an embodiment of a memory systemin accordance with the invention;

FIG. 21 is a schematic block diagram of another embodiment of a memorysystem in accordance with the invention;

FIG. 22 is a state diagram of an example embodiment of a memory systemin accordance with the invention;

FIG. 23 is a state diagram of another example embodiment of a memorysystem in accordance with the invention;

FIG. 24 is a schematic block diagram of another embodiment of a memorymapping in accordance with the invention; and

FIG. 25 is a schematic block diagram of another embodiment of a memorysystem in accordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of an embodiment of a computingsystem that includes user devices 10-14, a memory system 16, a database18, a server 20, a local area network (LAN) 22, a router 24, and a modem26. Each of the user devices 10-14 may be a portable device or a fixeddevice. For example, a portable device may be a cell phone, a smartphone, a personal digital assistant, a digital music player, a digitalvideo player, a laptop computer, a handheld computer, a video gamecontroller, and/or any other portable computing equipment. A fixeddevice may be a personal computer, a computer server, a cable set-topbox, a satellite receiver, a television set, a printer, a fax machine,home entertainment equipment, a video game console, and/or any type ofhome or office computing equipment.

Each of the user device 10-14 includes a computing core 34, 42, 50,non-core memory 32, 40, 48, and an interface 38, 46, 54 to communicatewith the LAN 22. The interface 38, 46, 54 accommodates one or morestorage system standards such that the user device 10-14 can utilize astorage standard native to its operating system and/or the DSN protocol.The non-core memory 32, 49, 48 is memory outside of the computing core34, 42, 50 but closely associated with the computing core 34, 42, 50.For example, non-core memory 32, 49, 48 may include a hard disk drive,an external FLASH memory, and an external DSN memory. The computing core34, 42, 50 may include the processing module, a core memory (mainmemory) 36, 44, 52, and the memory controller as will be described ingreater detail with reference to FIG. 2.

In addition, each of the memory system 16, the database 18, the server20, the router 24, and the modem 26 may be a portable device or a fixeddevice or may be a functional module within another unit that is aportable device or a fixed device. For example, the server 20 may be acomputer server and the memory system 16 may be a functional moduleoperating on the server 20. In another example, the server 20 may be afunctional module operating on one of the user devices 10-14.

The LAN 22 may be a wire line and/or wireless communication system orsystem of systems that provide communications capability between theuser devices 10-14, the memory system 16, the database 18, the server20, and the router 24. The system of systems may be a combination ofprivate intranets and/or the public internet systems.

The modem 26, which may be a wire line or wireless modem, providescoupling between the LAN 22 and another network, which may be a wireline and/or wireless wide area network (WAN) communication system orsystem of systems that provide communications capability between theother network and the LAN 22. In an example, the modem 26 accesses theother network via an optical sub-network. In another example, the modem26 accesses the other network via a 4G Long Term Evolution (LTE)wireless network.

The router 24 interfaces the LAN 22 with the other network such thatdata is forwarded from the other network to the LAN 22 and from the LAN22 to the other network. The router 24 may be a wire lined and/orwireless capable to communicate with the other devices sharing the LAN22.

The database 18 may include one or more storage devices to centralizestorage of data. The data may include a data file, data blocks, a realtime data stream, and/or any other type of digital information. Forexample, the database 18 has an access protocol that mimics aconventional file system interface (e.g., file system (NFS), flash filesystem (FFS), disk file system (DFS), small computer system interface(SCSI), internet small computer system interface (iSCSI), file transferprotocol (FTP), web-based distributed authoring and versioning (WebDAV),etc.). As another example, the database 18 may utilize a dispersedstorage network (DSN) protocol as will be described with reference toone or more of FIGS. 3-8.

The server 20 includes an interface 28 and a computing core 30. Theinterface 28 provides communication with the LAN 22 and accommodates oneor more storage system standards such that the server 20 can utilize astorage standard native to its operating system and/or the DSN protocol.The server 20 facilitates storage and retrieval of data files, systemprograms, and/or user applications requested by the user device 10-14.Note that the data files, system programs, and/or user applications arestored in a dispersed fashion amongst one or more of the user devices10-14, the memory system 16, the database 18, the server 20, the router24, the modem 26, and/or another network via the modem 26. The method ofstoring and retrieval of data files, system programs, and/or userapplications will be discussed in greater detail with reference to oneor more of FIGS. 2-25.

The memory system 16 may include one or more storage devices and acomputing core to facilitate the storage of data. The data may include adata file, data blocks, a real time data stream, and/or any other typeof digital information. For example, the memory system 16 may include anaccess protocol that mimics a conventional file system interface and maybe any one or more of network file system (NFS), flash file system(FFS), disk file system (DFS), small computer system interface (SCSI),internet small computer system interface (iSCSI), file transfer protocol(FTP), and web-based distributed authoring and versioning (WebDAV). Asanother example, the memory system 16 may utilize a dispersed storagenetwork (DSN) protocol as will be described in greater detail withreference to FIGS. 3-8.

In an example of data storage, a computing core of a user device 10-14generates sets of error coded (EC) data slices from the data using anerror coding dispersal function (e.g., forward error correction, erasurecode, IDA, Reed-Solomon, convolutional coding, Trellis coding, Turbocoding, etc.). For example, the computing core may generate the EC dataslices by dividing the data (or data object) into Y data segments, errorcode each of the Y data segments, and slice an encoded data segment intoX (e.g., # of pillars) EC data slices; thus creating XY total errorcoded data slices from the data, or data object. The number of pillars Xper data segment is based on the error coding dispersal function and thesize of a data segment may be a fixed size (e.g., 1 MB), may be avariable size to achieve a fixed number of data segments (e.g., Y=sizeof data/# of segments), or may be a variable size for a varying numberof segments.

After generating the EC slices for a data segment, the computing core34, 42, or 50 determines where to store them. For example, the computingcore may determine to store the EC data slices in core memory, innon-core memory, in the memory system 16, in the database 18, and/or onthe network via the router 24 and the modem 26. As a specific example,the computing core may determine to store the EC data slices in memorydevices of the core memory, in memory devices of the non-core memory, inmemory devices of the memory system, in memory devices of the database,or in memory devices of the network. As another specific example, thecomputing core may determine to store the EC data slices across thevarious memories. For instance, one or more EC data slices may be storedin core memory, one or more EC data slices may be stored in non-corememory, one or more slices in the memory system, one or more slices inthe database, and one or more slices on network memory. Such adetermination may be based on one or more of a resiliency goal, aperformance goal, a cost goal, a memory utilization metric, apredetermined pattern, a user driven pattern, a prioritizationalgorithm, a data object type to DSN level mapping, and/or any otherfactor regarding effectiveness and/or performance of data storage.

Having determined where to store the EC data slices of a data segment,the computing core addresses X memory devices of the targeted memory forstoring the EC data slices. In this manner, each EC data slice of a datasegment is stored on a different memory device, which allows formultiple memory devices (e.g., X-T, where T is the read threshold forthe error coding dispersal function) to fail and the data segment tostill be accurately recovered. The computing core 34, 42, 50 saves thestorage locations of the EC data slices in a table to facilitatesubsequent retrieval of the data segment.

In an example of data retrieval, a computing core 34, 42, 50 of a userdevice 10-14 determines where the desired EC data slices are storedusing the table of storage locations. Having identified the memorydevices storing the EC data slices, the computing core 34, 42, or 50addresses the memory devices (e.g., core memory, non-core memory, memorysystem, the database, LAN storage, WAN storage) to retrieve the EC dataslices. Once the computing core 34, 42, or 50 has received a readthreshold number of EC data slices, it decodes them in accordance withthe error coding dispersal function to recapture the original datasegment.

As another example of operation, the computing core 34, 42, 50 may moveEC data slices between the layers of memory hierarchy of the computersystem (e.g., core memory, local non-core memory and non-local non-corememory such as the memory system, the database, and the network memory).For instance, the computing core may move EC data slices from the corememory to the local non-core memory or to the non-local non-core memoryas may be required while executing one or more user and/or systemapplications.

FIG. 2 is a schematic block diagram of an embodiment of a computing core56 that includes one or more of a processing module 58, a memorycontroller 60, a video processing unit 62, a main memory 64 (e.g., corememory), an input output (TO) controller 66, an input output (TO)interface 68, an input device interface module 69, an output deviceinterface module 70, a read only memory basic input output system (ROMBIOS) 72, a peripheral component interconnect (PCI) interface 74, aperipheral interface(s) 76, and a plurality of interfaces 80-82. Thememory controller 60 includes a dispersed storage (DS) processing module94.

The processing module 58 may be a single processing device or aplurality of processing devices. Such a processing device may be amicroprocessor, micro-controller, digital signal processor,microcomputer, central processing unit, field programmable gate array,programmable logic device, state machine, logic circuitry, analogcircuitry, digital circuitry, and/or any device that manipulates signals(analog and/or digital) based on hard coding of the circuitry and/oroperational instructions. The processing module may have an associatedmemory and/or memory element, which may be a single memory device, aplurality of memory devices, and/or embedded circuitry of the processingmodule. Such a memory device may be a read-only memory, random accessmemory, volatile memory, non-volatile memory, static memory, dynamicmemory, flash memory, cache memory, and/or any device that storesdigital information. Note that if the processing module includes morethan one processing device, the processing devices may be centrallylocated (e.g., directly coupled together via a wired and/or wireless busstructure) or may be distributedly located (e.g., cloud computing viaindirect coupling via a local area network and/or a wide area network).Further note that when the processing module implements one or more ofits functions via a state machine, analog circuitry, digital circuitry,and/or logic circuitry, the memory and/or memory element storing thecorresponding operational instructions may be embedded within, orexternal to, the circuitry comprising the state machine, analogcircuitry, digital circuitry, and/or logic circuitry. Still further notethat, the memory element stores, and the processing module executes,hard coded and/or operational instructions corresponding to at leastsome of the steps and/or functions illustrated in FIGS. 1-25. Ingeneral, the processing module 58 coordinates a majority of the tasks(e.g., execute one or more operation instructions of an algorithm,perform an interrupt, perform a co-processing function, process data,store data to memory, read data from memory, etc.) performed by thecomputing core 56.

The IO controller 66 provides access to the memory controller 60 fortypically slower devices via the IO interface 68 and/or the peripheralcomponent interface 74. The peripheral component interface 74 is coupledto one or more peripheral interfaces 78 and a plurality of memoryinterfaces 80 and 82. The IO interface 68 is coupled to one or moreinput device interfaces 69, one or more output device interfaces 70, anda ROM BIOS module 72. Each of the interfaces 69, 70, 76, 80, and 82includes hardware and/or software to support the electrical, functional,and/or mechanical coupling of the corresponding component to thecomputing core 56. For example, the input device interface 69 couples aninput device (e.g., mouse, keyboard, microphone, etc.) to the computingcore; the output device interface 70 couples an output device (e.g.,monitor, printer, speaker, etc.) to the computer core; and theperipheral interface 76 couples a peripheral component 78 (e.g., digitalimage sensor, a sound card, a USB memory, a hard disk controller, a TVtuner, and/or any other computer peripheral) to the computing core.

The memory interfaces 80 and 82 couple memory devices (e.g., non-core84-90, LAN and/or WAN memory 92) to the computing core. For example, oneof the memory interfaces 82 may couple a local area network (LAN) and/orwide area network (WAN) memory device 92 to the computing core inaccordance with a NFS standard, DSN protocol, and/or other standardizedprotocol. The memory interface 80 may couple a non-core flash memory tothe computing core in accordance with a flash file system (FFS)standard, a DSN protocol, and/or other standardized protocol. A harddrive may interface with the interface utilizing a disk file system(DFS). One of the memory interfaces 82 may couple a non-core hard driveto the computing core in accordance with NFS, FFS, DFS, DSN and/or otherstandardized protocol. The DSN protocol will be described in greaterdetail with reference to one or more of FIGS. 3-25.

Each of the memories (e.g., the main memory 64, the ROM BIOS 72, thenon-core flash memory 84, the non-core hard drive 86-90, and the LANand/or WAN memory 92) may include a plurality of separately addressablememory devices. Each of the separately addressable memory devices maystore one or more error coded (EC) data slices of data. For example, ifa data object is divided into 10 data segments and each data segment iserror encoded and sliced into 8 EC data slices, then a first memorydevice will store the first EC slices of each data segment, a secondmemory device will store the second EC data slices of each data segment,and so on.

At the start-up or rebooting of the device incorporating the computingcore, the processing module 58 retrieves, and subsequently executes, abasic input output system (BIOS) program (e.g., instructions toinitialize and test at least some of the hardware and/or softwareelements of the computing core 56 and/or the device) from the ROM BIOS72 and/or other memory location. For example, all of the BIOS executableinstructions may be stored in the ROM BIOS 72 as a plurality of EC dataslices. In this example, the DS processing module 94 of the memorycontroller 94 decodes the EC data slices in accordance with an errorcoding dispersal function to retrieve the BIOS program. Alternatively,the processing module 58 may include a DS processing function to decodethe EC data slices.

In another example, the BIOS program is encoded as a plurality of ECdata slices, where some of the slices are stored in the ROM BIOS 72 andthe remaining slices are stored in the LAN and/or WAN memory 92. In thisinstance, the DS processing module 94 retrieves the slices andreconstructs the instructions of the BIOS program therefrom. In anotherexample, the BIOS program is encoded as a plurality of EC data slices,which are stored in the LAN and/or WAN memory 92. In this instance, theROM BIOS 72 may store pointer information regarding the LAN and/or WANmemory 92 storing the BIOS program. As yet another example, the ROM BIOS72 may store the instructions, or a sub-set of instructions, of the BIOSprogram in a raw format (e.g., non-encoded). The ROM BIOS 72 and accessthereof will be discussed in greater detail with reference to one ormore of FIGS. 9, 11-13, and 15-16.

Once the BIOS program is executed or during its execution, theprocessing module 58 and/or the memory controller 60 retrieves anoperating system (OS) and the processing module 58 executes instructionsof the OS. For example, the memory controller 60 retrieves instructionsof the operating system (OS) from non-core memory 84-90 and/or theLAN-WAN memory 92 and stores the instructions in main memory 64. The OSmay be stored in non-core memory 84-90 and/or LAN-WAN memory 92 in a rawformat and/or in an error coding dispersal function format (i.e., as ECdata slices). If the OS is stored as EC data slices, the DS processingmodule 94 decodes them prior to providing them to the processing module56.

When the OS is operational, the processing module 56, via the memorycontroller 60, may retrieve user applications (e.g., work processing,database, spreadsheet, drawing, web browser, etc.) and/or systemapplications from the non-core memory 84-90 and/or the LAN-WAN memory92. The user and/or system applications may be stored in non-core memory84-90 and/or LAN-WAN memory 92 in a raw format and/or in an error codingdispersal function format (i.e., as EC data slices). If the user and/orsystem applications are stored as EC data slices, the DS processingmodule 94 decodes them prior to providing them to the processing module56.

As the processing module 56 is executing a user application and/orsystem application, it may requiring the reading and/or writing of datato the memory of the device (e.g., main memory, non-core memory 84-90,and/or LAN-WAN memory 92). For writing of data, the memory controller 60creates EC data slice (in pillars) of the data and disperses them forstorage across main memory 64, non-core memory 84-90, and/or LAN and/orWAN memory 92. For reading of data, the memory controller 60 addressesthe memory devices storing the EC data slices of the requested data.When a threshold number of the EC data slices are received for a givendata segment, the DS processing module 94 reconstructs the data segmentfrom the received EC data slices.

As another example, the memory controller 60 may store and retrieve datain the main memory in a raw format for use by the processing module 56.When the data in main memory is to be written to non-core memory, the DSprocessing module encodes the data and disperses the EC data slices tothe non-core memory. The method of retrieving user applicationexecutable instructions will be discussed in greater detail withreference to FIGS. 18-19.

FIG. 3 is a schematic block diagram of an embodiment of a dispersedstorage (DS) processing module 94 of memory controller 60. The DSprocessing module 94 includes a gateway module 98, an access module 100,a grid module 102, a storage module 104, and may further include abypass/feedback path (not shown) from the storage module to the accessmodule. The DS processing module 94 may also include an interface 96 anda DS interface 106.

In an example of storing data, the gateway module 96 of the DSprocessing module 94 receives an incoming data object (e.g., a datafile, a data block, an EC data slice, etc.), authenticates the componentassociated with the data object, obtains component information of theauthenticated user, and assigns a source name to the data object inaccordance with the component information. To authenticate a component,the gateway module 98 verifies a component ID (e.g., ID of theprocessing module, main memory, non-core memory, and/or the LAN-WANmemory). If the ID is verified, the gateway module 98 retrieves thecomponent information, which includes a vault identifier, operationalparameters, and component attributes. A vault identifier identifies avault, which is a virtual memory space that maps to a set of memorydevices (e.g., the main memory, the non-core memory, and/or the LAN-WANmemory). For example, a first vault may include eight non-core memorydevices (X=8 wide) and a second vault may include sixteen LAN-WAN memorydevices (X=16 wide). The operational parameters may include an errorcoding algorithm, the width n (number of pillars X or slices per segmentfor this vault), a read threshold T, an encryption algorithm, a slicingparameter, a compression algorithm, an integrity check method, cachingsettings, parallelism settings, and/or other parameters that may be usedto access the DSN memory layer.

The gateway module 98 determines the source name to associate with thedata object based on the vault identifier and the data object. Forexample, the source name may contain a data name (block number or a filenumber), the vault generation number, a reserved field, and a vaultidentifier. The data name may be randomly assigned but is associatedwith the user data object.

The gateway module 98 may utilize the bypass/feedback path to transferan incoming EC data slice from one memory device to another when the DSprocessing module 94 determines that the EC data should be transferredwithout decoding. For example, EC data slices may be transferred frommain memory to non-core memory and/or to WAN-LAN memory without decodingin accordance with the error coding dispersal function.

The access module 100 receives the data object and creates a series ofdata segments 1 through Y therefrom. The number of segments Y may bechosen or random based on a selected segment size and the size of thedata object. For example, if the number of segments is chosen to be afixed number, then the size of the segments varies as a function of thesize of the data object. For instance, if the data object is an imagefile of 4,194,304 eight bit bytes (e.g., 33,554,432 bits) and the numberof segments Y=131,072, then each segment is 256 bits or 32 bytes. Asanother example, if segment size is fixed, then the number of segments Yvaries based on the size of data object. For instance, if the dataobject is an image file of 4,194,304 bytes and the fixed size of eachsegment is 4,096 bytes, then the number of segments Y=1,024. Note thateach segment is associated with the source name.

The grid module 102, as will be discussed in greater detail withreference to FIG. 6, may pre-manipulate (e.g., compression, encryption,cyclic redundancy check (CRC), etc.) the data segment before creating Xerror coded data slices for each data segment. The grid module 102creates XY error coded data slices for the Y data segments of the dataobject and adds forward error correction bits to the data segment bitsin accordance with an error coding algorithm (e.g., Reed-Solomon,Convolution encoding, Trellis encoding, etc.) to produce an encoded datasegment. The grid module 102 determines the slice name and attaches theunique slice name to each EC data slice.

The number of pillars, or slices X per data segment (e.g., X=16) ischosen as a function of the error coding objectives. The DS processingmodule may utilize different error coding parameters for EC data slicesbased on guidance from one or more of vault parameters (e.g., a readthreshold), a command from the processing module, priority of the ECdata slice, type of data in the EC data slice, and/or retrieval speedrequirements. Note that a read threshold T (e.g., T=10) of the errorcoding algorithm is the minimum number of error-free error coded dataslices required to be able to reconstruct a data segment. For instance,the DS processing module 94 can compensate for X-T (e.g., 16−10=6)missing, out-of-date, and/or corrupted error coded data slices per datasegment.

The grid module 100 receives each data segment 1-Y and, for each datasegment, generates X number of error coded (EC) slices using an errorcoding dispersal function. The grid module 100 also determines thememory devices for storing the EC data slices based on a dispersedstorage memory mapping associated with the memory device(s), associatedwith the component's vault, and/or memory device attributes, whichinclude availability, self-selection, performance history, link speed,link latency, ownership, available DSN memory, domain, cost, aprioritization scheme, a centralized selection message from anothersource, a lookup table, data ownership, and/or any other factor tooptimize the operation of the computing system. In this embodiment, thegrid module 100 is designating main memory 64 for storing EC data slicesof pillar 1, non-core memory device 84 for storing EC data slices ofpillar 2, non-core memory 86 for storing EC data slices of pillar 3, andso on.

The storage module 104 may perform integrity checks on the EC dataslices and then transmit the EC data slices 1 through X of each segment1 through Y to the designated memory devices. The DS storage module 94may store the EC data slices and locally keep a table to convert virtualDSN addresses into physical storage addresses. Note that the number oftargeted memory devices is equal to or greater than the number ofpillars (slices X per segment) so that no more than one error coded dataslice of the same data segment is stored on the same memory device.Further note that EC data slices of the same pillar number but ofdifferent segments (e.g., EC data slice 1 of data segment 1 and EC dataslice 1 of data segment 2) may be stored on the same or different memorydevices.

In an example of a read operation, the DS processing module 94 receivesa read request, which it authenticates. When the request is authentic,the DS processing 94 sends a read message to each of the memory devices(e.g., main memory and the non-core memories) storing slices of the dataobject being read. The slices are received by the storage module 104,which performs a parity check and provides the slices to the grid module102. The grid module 102 de-slices and decodes the slices of a datasegment to reconstruct the data segment. The access module 100reconstructs the data object from the data segments and the gatewaymodule 98 formats the data object for transmission to the processingmodule, peripheral device, I/O device, or other targeted component ofthe computer system.

FIG. 4 is a schematic block diagram of an embodiment of a dispersedstorage (DS) processing module 94 similar to that of FIG. 3. In thisembodiment, the EC data slices are stored and retrieved from a pluralityof non-core memory devices.

FIG. 5 is a schematic block diagram of an embodiment of a dispersedstorage (DS) processing module 94 similar to that of FIG. 3. In thisembodiment, the EC data slices are stored and retrieved from a pluralityof memory devices of the main memory.

FIG. 6 is a schematic block diagram of an embodiment of a grid module102 that includes a control unit 112, a pre-data manipulator 114, anencoder 116, a slicer 118, a post-data manipulator 120, a pre-datade-manipulator 122, a decoder 124, a de-slicer 126, and a post-datade-manipulator 128. Note that the control unit 112 may be partially orcompletely external to the grid module 102. For example, the controlunit 112 may be part of the computing core, part of a user device, or ina system manager.

The control unit 112 may assist and/or control the other elements of thegrid module 102 to determine operational parameters that may include thetypes of pre-data and post-data manipulation/de-manipulation are to beapplied to an incoming/outgoing data segments 130, if any, the type oferror encoding/decoding to apply to the (encoded) data segments 132, andthe slicing/de-slicing function. In addition, the control unit 112 mayfurther create and maintain a distributed storage memory mapping, statusof the various memory device, performance history of the memory devices,capability of the memory devices, prioritization information for memorydevice usage, and rebuilding criteria (e.g., when to rebuild, when togather integrity information, etc.). The control unit 112 may determinethe operational parameters by combining parameters of the associatedvault with other parameters, which will be discussed below.

In an example of operation, the pre-data manipulator 88 receives thedata segment 104 and a write instruction from an authorized device(e.g., the processing module) or is generated by the memory controller.The control unit 112 or gateway module may assist the pre-datamanipulator 114 to determine the vault for this data segment 130. Whenenabled, the pre-data manipulator 114 determines if pre-manipulation ofthe data segment 130 is required, and if so, what type ofpre-manipulation. The determination may be based on one or more factorsincluding a computing system-wide predetermination, a table lookup,vault parameters associated with the user identification, the type ofdata, security requirements, available DSN memory, performancerequirements, and/or other metadata.

The pre-data manipulator 114 manipulates the data segment in accordancewith the manipulation determination, which includes one or more ofcompression (e.g., Lempel-Ziv-Welch, Huffman, Golomb, fractal, wavelet,etc.), signatures (e.g., Digital Signature Algorithm (DSA), EllipticCurve DSA, Secure Hash Algorithm, etc.), watermarking, tagging,encryption (e.g., Data Encryption Standard, Advanced EncryptionStandard, etc.), adding metadata (e.g., time/date stamping, userinformation, file type, etc.), cyclic redundancy check (e.g., CRC32),and/or other manipulations to enhance the value of the data segment 104.Note that the pre-data de-manipulator 122 performs the complementaryfunctions of the pre-data manipulator 114 when data is retrieved fromthe memory devices. Note that the pre-data manipulator 114 and pre-datade-manipulator 122 are bypassed when data is recovered and reconstructedin the rebuild path.

The encoder 116 receives the data segment 130 from the pre-datamanipulator 114 and encodes the data segment using an error codingfunction (e.g., FEC, Reed-Solomon, etc.) to produce the encoded datasegment 106. The encoder 116 determines what type of encoding algorithmto use based on factors including predetermination in the vault for thedata segment 104, a time based algorithm, user directed, DS managingunit directed, as a function of the data type, as a function of the datasegment metadata, and/or any other factor to determine algorithm type.The encoder may utilize a different encoding algorithm for each datasegment, the same encoding algorithm for all data segments, or someother combination. The encoder may determine the encoding algorithm typeto be one of Golay, Multidimensional parity, Reed-Solomon, Hamming, BoseRay Chauduri Hocquenghem (BCH), Cauchy-Reed-Solomon, or any other FECencoder. Note that the encoded data segment 132 is of greater size thanthe data segment 130 by the overhead rate of the encoding algorithm. Forinstance, the encoded data segment is d(X/T), where d is size of thedata segment, X is the width n or number of slices, and T is thethreshold or minimum number of received slices to enable recreation ofthe data segment.

The corresponding decoding process performed by decoder 124 canaccurately recover the data segment provided it receives T or moreslices. For example, if X=16 and T=10, then the data segment 130 will berecoverable even if 6 EC data slices per segment are corrupted ormissing. Note that the decoder 124 performs the complementary functionsof the encoder 124 when data is retrieved from the DSN memory.

The slicer 118 receives the encoded data segment 132 and transforms itinto EC data slices in accordance with the slicing parameter from thevault for this requesting component and/or data segment. For example,data segments are packed one for one into a data slice. In thisinstance, it is possible to correct many data slices with this method ifthe error patterns are substantially manifested as individual biterrors. In another example, entire slices may be lost and hence entiredata segments may not be recoverable. In another embodiment, a datasegment is dispersed across many data slices (e.g., X wide pillars) tolessen the impact on a given data segment when an entire data slice islost. Less data per segment is lost, when a data slice is lost, as thedata segment is dispersed across more slices. The slicing is discussedin greater detail with reference to FIG. 5. Note that the de-slicer 100performs the complementary functions of the slicer 92 when data isretrieved from the DSN memory.

The post-data manipulator 120 receives EC data slices and determines ifpost-manipulation of the EC data slices is required, and if so, whattype of post-manipulation. The determination may be driven by one ormore factors including a computing system-wide predetermination,parameters in the vault for this user, a table lookup, the useridentification, the type of data, security requirements, available DSNmemory, performance requirements, and/or other metadata. The post-datamanipulator manipulates the EC data slice in accordance with themanipulation determination. The manipulation may include one or more ofslice level compression, signatures, encryption, CRC, addressing,watermarking, tagging, adding metadata, and/or other manipulation toimprove the effectiveness of the computing system. The post-datamanipulator passes the resulting EC data slices, with the attached slicename, to the storage module for storage in the DSN memory. Note that thepost-data de-manipulator 126 performs the complementary functions of thepost-data manipulator 120 when data is retrieved from the memorydevices.

In an example of operation, the grid module 110 performs a rebuilderoperation to repair a particular data segment that has known missing,out-dated, and/or corrupted EC data slices. When one or more slices of adata segment are to be rebuilt, the grid module retrieves at least T ECdata slices (e.g., T=read threshold) of slices of the data segment thatdo not have a data inconsistency. In addition, the grid module mayretrieve vault parameters based on a vault identifier contained in theslice name, wherein the vault parameters include information regardingthe type of post-data manipulation, the slicing/de-slicing function, andthe encoding/decoding function. Based on these parameters, the retrievedslices are post-data de-manipulated, de-sliced, and decoded to produce areconstructed data segment. The reconstructed data segment is thenencoded, sliced, and post-data manipulated to produce a plurality ofrebuilt data slices that are sent to the memory devices for storage.

FIG. 7 is a diagram of an example embodiment of error coded data slicecreation where the slicer creates four EC data slices from a thirty-twobit encoded data segment. The slicer disperses the bits from the encodeddata segment across the EC data slices wrapping around from the lastslice to the first slice over and over (i.e., interleaves the bits amongthe slices). Each EC data slice, for this data segment, is stored on adifferent DS storage unit. In this example, encoded data segment bits 0,4, 8, 12, 16, 20, 24, and 28 form EC data slice 1; encoded data segmentbits 1, 5, 9, 13, 17, 25, and 29 form EC data slice 2; encoded datasegment bits 2, 6, 10, 14, 18, 22, 26, and 30 form EC data slice 3; andencoded data segment bits 3, 7, 11, 15, 19, 23, 27, and 31 form EC dataslice 4. In a 4/3 system (a width of 4 pillars and a read threshold of3), one EC data slice can be lost and the data segment can still beaccurately recovered. Note that more slices produce a larger distancebetween consecutive encoded data segment bits of a slice, which improvesthe error resiliency.

FIG. 8 is a schematic block diagram of an embodiment of a computersystem's a memory map that includes a kernel block, a user block, and anunused block. The blocks may be associated with physical memoryaddresses or the blocks may be associated with virtual memory where thephysical memory may be fragmented within a first memory type (e.g., corememory) or overflow to a second memory type (e.g., non-core memory). Thekernel block is an area of memory exclusive to the operating system(OS). The user block is typically used to store applications (e.g.,instructions and/or data of an application). The unused block is sparememory in an instantaneous sense as it may be used for future expansionof more applications and for other uses on a temporary basis (e.g., datacaching).

In this example, the memory is divided into a four pillar DSN (dispersedstorage network) memory set, where first EC data slices of data segmentsare stored in pillar 1, second EC data slices of the data segments arestored in pillar 2, and so on. Alternatively, a data object may bestored as raw data (i.e., not dispersed error coded) in one to all fourof the pillars. Each pillar may be the same memory type (e.g., all mainmemory), or the pillars may include different memory types (e.g., onecore, a second non-core, a third LAN memory, and a fourth WAN memory).Note that a computing system may include one or more DSN memory sets andeach may have a different number of pillars. For example, the kernel mayutilize a first DSN memory set and the applications may utilize a secondDSN memory set. As such, the operating system may be stored as a seriesof EC data slices and/or as raw data in the kernel section; softwaredrivers may be stored as a series of EC data slices and/or raw data inthe kernel section or in the user section; applications may be stored asa series of EC data slices and/or raw data in the user section; and theAPI (application program interface) may be stored as a series of EC dataslices and/or as raw data in the kernel section and/or the user section.

FIG. 9 is a schematic block diagram of another embodiment of thecomputing core coupled to one or more non-core memories 164 and/or toone or more LAN/WAN memories 166. The computing core includes one ormore processing modules 156-158, main memory 162, a memory controller134, a video processing unit 160, a plurality of ROM, an TO controller172, and TO interface, 170, and a DS memory interface module 168. Thememory controller 134 includes a memory processor unit 136, aninstruction cache 138, a data cache 140, a memory interface 144, abuffer 142, an input/request unit 146, an output unit 148, multiplexers152-154, and the DS processing module 150.

The main memory 162 includes a plurality of random access memory (RAM)and may store data in a raw format (e.g., not EC data slices) or in anerror coding dispersal format (e.g., as EC data slices). The data storedin main memory 162 may be BIOS instructions, OS instructions,application instructions, application configuration data, and/orapplication operational data.

The plurality of ROM stores at least a portion of the BIOS program. Theinstructions of the BIOS program may be stored in the raw format (e.g.,not EC data slices) or in the error coding dispersal format.

The non-core memory 164, and LAN/WAN memory 166 may connect to thememory controller 134 via the 10 controller 172 and 10 interface 170.The LAN/WAN memory 166 may interface with the 10 interface 170 via adispersed storage (DS) memory interface module 168. The non-core memory164, and LAN/WAN memory 166 may store data information in the raw format(e.g., not EC data slices) or in the error coding dispersal format.

In general, the memory controller 134 fetches executable instructionsfor one or more processing modules 156-158, transfers data between thecomponents of the computing system (e.g., the processing module, theperipheral devices, the video processing unit 160, the main memory 162,the ROM, the non-core memory 164, and the LAN/WAN memory 166), andfacilitates reading and writing of data in memory. As part of thefetching of instructions and as part of the reading and writing of data,the memory controller 134 determines whether the instructions and/ordata is:

is encoded in accordance with an error coding dispersal function and isto be decoded;

is encoded in accordance with the error coding dispersal function and isto remain encoded;

is encoded in accordance with the error coding dispersal function and isto be encoded in accordance with a different error coding dispersalfunction;

is in the raw data format and to be encoded in accordance with the errorcoding dispersal function; and/or

is in the raw data format and to remain in the raw data format.

In an example of operation, the processing module 156-158 sends arequest to fetch BIOS instructions to the input/request unit 146. Thememory processor unit 136 determines where the BIOS instructions arelocated by accessing a DSN data to physical memory lookup table. Thememory processor unit 136 issues a command to the output unit 148 tosend read commands to the ROM to retrieve EC data slices. Theinput/request unit 146 receives EC data slices from the ROM and sendsthem to the DS processing module 150 via the memory interface 144. Thememory processor unit 136 temporarily holds the EC data slices in one ormore of the data cache 140 or buffer 142 if the DS processing module 150is not available to receive the EC data slices. When the DS processingmodule 150 is available, it receives the EC data slices and convertsthem into raw BIOS instructions and sends the BIOS instructions to theoutput unit 148 via the buffer 142.

The memory processor unit 136 directs the output unit 148 to output theraw BIOS executable instructions for storage in one or more of the mainmemory 162, the non-core memory 164, and/or the LAN/WAN memory 166. Oncethe BIOS instructions are stored, the memory controller unit 134 fetchesthem and transfers them to the processing module 156-158. Alternatively,the raw BIOS instructions may be directly outputted to the processingmodule 156-158.

In another example of operation, the processing module 156-158 instructsthe memory controller 134 to save an application data result. The memoryprocessor unit 136 determines where to store the application data resultand in what format by based on information in the memory map. The memoryprocessor unit 136 then issues a command to the output unit 148 to sendread commands to the main memory 162 to retrieve application dataresult. The input/request unit 146 receives the application data resultfrom the main memory 162 and sends it to the DS processing module 150via the memory interface 144 when it is to be error encoded. The memoryprocessor unit 136 temporarily stores the application data result in thebuffer until DS processing module 150 is available to convert theapplication data result into EC data slices.

The memory processor unit 136 then directs the output unit 148 to storethe EC data slices from the buffer 142 in one or more of the main memory162, the non-core memory 164, and/or the LAN/WAN memory 166 based on theDSN data to physical memory lookup table.

In another example of operation, the processing module 156-158 sends arequest to transfer a data object (in EC data slices in the DSN) fromone DSN memory to another. The memory processor unit 136 determineswhere the data object EC slices are located by accessing the DSN data tophysical memory lookup table. The memory processor unit 136 issues acommand to the output unit 148 to send read commands to the WAN memory166. The input/request unit 146 receives EC data slices from the WANmemory 166 and sends them to the DS processing module 150 via the memoryinterface 144. The DS processing module 150 converts the EC data slicesinto destination EC data slices using another error coding dispersalfunction and sends the destination EC data slices to the output unit 148via the buffer 142.

The memory processor unit 136 directs the output unit 148 to store thedestination EC data slices from the buffer 142 in one or more of themain memory 162, the non-core memory 164, and/or the LAN/WAN memory 166based on the DSN data to physical memory lookup table.

In another example, the input/request unit 146 receives the memoryaccess request and forwards it to the memory processor unit. The memoryprocessor unit interprets the memory access requests to determinewhether an error coding dispersal function is to be applied to a datasegment to produce an error coded processed data segment (e.g., encodeand slice a data segment to produce EC data slices), the error codingdispersal function is to be applied to an error coded processed datasegment to reconstruct the data segment (e.g., de-slice and decode ECdata slices to produce the data segment), the error coding dispersalfunction is not to be applied to the data segment (e.g., transferring adata segment in a non-distributed format), or if the error codingdispersal function is not to be applied to the error coded processeddata segment (e.g., transferring EC data slices). The determination maybe based on one or more of but not limited to information in the memoryaccess request, an object ID, a filename, a virtual memory address, auser ID, the process ID, a vault ID, a vault lookup, a predetermination,a list, a command, and/or a message.

The memory processor unit determines a destination of the data segmentor of the error coded processed data segment, wherein the destination isone of the distributed storage processing module, the memory interface,the temporary memory, and the output unit. The determination may bebased on one or more of but not limited to information in the memoryaccess request, a virtual memory addresses to physical memory addresstable lookup, an object ID, a filename, a virtual memory address, a userID, the process ID, a vault ID, a vault lookup, a predetermination, alist, a command, and/or a message.

The memory processor unit generates a data routing signal based on theinterpreting of the memory access request (e.g., how to route). Theinput/request unit forwards the data segment or the error codedprocessed data segment associated with the memory access request to thedestination in accordance with the data routing signal.

In another example, the memory controller 134 includes the DS processingmodule 150 and a memory control processing module. The memory controlprocessing module may include one or more of the multiplexers 152-154,the input/request unit 146, the memory processor unit 136, the memoryinterface 144, the instruction cache 138, the data cache 140, the buffer142, and/or the output unit 148.

In an example of operation, the memory control processing modulereceives a memory access request regarding a data segment. The DSprocessing module may interpret the memory access request to determinevault information facilitates storage of the vault information. Thevault information may include one or more of but not limited to avirtual memory address to distributed physical address table, an objectID, a filename, the user ID, a vault ID, and/or operational parameters(e.g., pillar width, read threshold, write threshold, encoding method,slicing method, etc.).

The example continues, in a write scenario, with the memory controlprocessing module receiving a write command of the data segment as thememory access request. In a read scenario, the memory control processingmodule receives a read command of the data segment as the memory accessrequest. Note that the data segment may be stored in a memory of thecomputing system as EC data slices and/or in a non-distributed fashion(e.g., not as EC data slices). The memory control processing moduleinterprets the memory access request to determine whether an errorcoding dispersal function of the data segment is applicable. In otherwords, the memory control processing module determines if the datasegment is stored as EC data slices.

The memory control processing module converts a virtual memory addressof the data segment to a non-distributed physical address when the errorcoding dispersal function is not applicable. In other words, the memorycontrol processing module determines physical memory addresses when thedata segment is not stored as EC data slices. In a write scenario, thememory control processing module interprets the write command todetermine that the data segment is to be stored as a plurality of dataslices in accordance with the error coding dispersal function. In a readscenario, the memory control processing module interprets the readcommand to determine that the data segment is stored as the plurality ofdata slices in accordance with the error coding dispersal function. Inthe read scenario, the memory control processing module addresses aplurality of memories to retrieve the plurality of data slices to sendto the distributed storage processing module.

The example continues with the memory control processing module sendingthe memory access request to the distributed storage processing modulewhen the memory control processing module determines that the errorcoding dispersal function is applicable. In other words, the memorycontrol processing module activates the DS processing module when thedata segment is stored as EC data slices. The distributed storageprocessing module converts the virtual memory address of the datasegment to a plurality of distributed physical addresses when the errorcoding dispersal function is applicable. For instance, the distributedstorage processing module determines physical memory addresses where theEC data slices are stored where the determination may be based on one ormore of but not limited to the virtual memory address to distributedphysical address table, a table lookup, information in the memory accessrequest, an object ID, a filename, a virtual memory address, a user ID,a process ID, a vault ID, a vault lookup, a predetermination, a list, acommand, and/or a message.

The example continues with the distributed storage processing moduleperforming the error coding dispersal function on the data segment toproduce an error coded processed data segment. In a write scenario, thedistributed storage processing module performs the error codingdispersal function on the data segment to produce the plurality of dataslices as the error coded processed data segment in accordance withoperational parameters (e.g., pillar width, read threshold, encodingmethod, slicing method, etc.). In a read scenario, the distributedstorage processing module performs the error coding dispersal functionon the plurality of data slices to produce a reconstructed data segmentas the error coded processed data segment in accordance with theoperational parameters.

The example continues with the distributed storage processing modulessending the error coded processed data segment to the memory controlprocessing module. In a write scenario, the memory control processingmodule addresses a plurality of memories to store the plurality of dataslices. In a read scenario, the memory control processing module maysend the reconstructed data segment to another module or unit of thecomputing system. Note that the method of the embodiment discussed abovemay repeat for a plurality of data segments, wherein a data objectcomprises a plurality of data segments.

FIG. 10 is a logic diagram of an embodiment of a method for datahandling where the memory controller transfers data from one memory toanother. The memory controller may receive a retrieve and/or storerequest from the processing module 174. The memory controller maydetermine a saved file type based on vault parameters and the DSN datato physical memory lookup table 176. The memory controller may retrievethe raw format file or data object when the saved file type is raw 178.

The memory controller may retrieve the EC data slices format when thetype is EC data slices 180. The memory controller may decode the EC dataslices into the raw format data object 182.

The memory controller may determine a store file type based on vaultparameters and the DSN data to physical memory lookup table 184. Thestore file type and store DSN memory level may be different than thesaved file type and saved DSN memory level to realize a different set ofresiliency and performance characteristics. For example, a dormant filethat is in WAN memory may be error coded and dispersed to provide goodprotection. The dormant file may be required to operate in main memorywith more speed of successive access steps. The memory controller maystore the raw format file or data object when the store file type is raw186.

The memory controller may encode raw format data object as EC dataslices format when the store file type is EC data slices 188. The memorycontroller may disperse the EC data slices by storing the EC data slicesin the DSN memory based on the DSN data to physical memory lookup table190.

In an embodiment, the memory controller includes an interface forcoupling to at least a memory device and a processing module operablycoupled to the interface. The memory device may be implemented in aplurality of memory layers where the memory layers may include the mainmemory, a local non-core memory, a local area network memory, and/or awide area network memory. For example, a first layer may include mainmemory associated with the computing core, a second layer may includelocal non-core memory such as a hard disk drive operably coupled to thecomputing core, a third layer may include local area network memory suchas non-core memory operably coupled via a local area network (e.g., ahard disk drive in another computing device in the same building), and afourth layer may include wide area network memory such as non-corememory operably coupled via a wide area network (e.g., a hard disk drivein another computing device that is not in the same building). Note thatany of the layers may be associated with any memory type.

In an example of operation, the processing module receives a datasegment memory transfer request from a first memory layer to a secondmemory layer. The processing module may interpret a read request orinterpret a write request based on the data segment memory transferrequest. For example, the data segment memory transfer request mayinclude a read request from the main memory (e.g., the first memorylayer) and a write request to the local area network memory (e.g., thesecond memory layer).

The processing module determines whether the data segment is storedwithin the first memory layer in accordance with an error codingdispersal function. The determination may be based on one or more of butnot limited to information in the data segment memory transfer request,an object ID, a filename, a virtual memory address, a virtual memoryaddress to distributed physical address table, a table lookup, a userID, a process ID, a vault ID, a vault lookup, a predetermination, alist, a command, and/or a message.

The processing module retrieves the data segment from the first memorylayer and determines whether to store the data segment in accordancewith a second error coding dispersal function in the second memory layerwhen the processing module determines that the data segment is notstored in accordance with the error coding dispersal function (e.g.,non-distributed). The determination may be based on one or more of butnot limited to information in the data segment memory transfer request,an object ID, a filename, a virtual memory address, a virtual memoryaddress to distributed physical address table, a table lookup, a userID, a process ID, a vault ID, a vault lookup, a predetermination, alist, a command, and/or a message.

The processing module performs the second error coding dispersalfunction on the data segment to produce a second plurality of dataslices and the processing module sends the second plurality of dataslices to the second memory layer when the data segment is to be storedin accordance with the second error coding dispersal function. Theprocessing module sends the data segment to the second memory layer whenthe data segment is not to be stored in accordance with the second errorcoding dispersal function (e.g., the non-distributed format data segmentis transferred as a non-distributed format data segment).

The processing module determines whether the data segment is to bestored in the second memory layer in accordance with the error codingdispersal function when the processing module determines that the datasegment is stored (e.g., in the first memory layer) in accordance withthe error coding dispersal function. The processing module retrieves aplurality of data slices from the first memory layer, may utilize abuffer to temporarily store the plurality of data slices, converts theplurality of data slices into a reconstructed data segment, anddetermines whether to store the reconstructed data segment in accordancewith the second error coding dispersal function in the second memorylayer when the processing module determines that the data segment is notto be stored in the second memory layer in accordance with the errorcoding dispersal function. The determination may be based on one or moreof but not limited to information in the data segment memory transferrequest, an object ID, a filename, a virtual memory address, a virtualmemory address to distributed physical address table, a table lookup, auser ID, a process ID, a vault ID, a vault lookup, a predetermination, alist, a command, and/or a message.

The processing module performs the second error coding dispersalfunction on the reconstructed data segment to produce the secondplurality of data slices and sends the second plurality of data slicesto the second memory layer when the reconstructed data segment is to bestored in accordance with the second error coding dispersal function.The processing module facilitates forwarding of the plurality of dataslices from the first memory layer to the second memory layer when theprocessing module determines that the data segment is to be stored inthe second memory layer in accordance with the error coding dispersalfunction. In other words, the processing module transfers the slicesdirectly from the first memory layer to the second memory layer sincethey are both substantially utilizing the same error coding dispersalfunction.

FIG. 11 is a schematic block diagram of another embodiment of thecomputing core coupled to one or more non-core memories 164 and/or toone or more LAN/WAN memories 166. The computing core includes one ormore processing modules 156-158, main memory 162, a memory controller134, a video processing unit 160, a plurality of ROM, an TO controller172, and TO interface, 170, and a DS memory interface module 168. Thememory controller 134 includes a memory processor unit 136, aninstruction cache 138, a data cache 140, a memory interface 144, abuffer 142, an input/request unit 146, an output unit 148, multiplexers152-154, a main memory interface 192, and the DS processing module 150.

This embodiment of the computing system is similar in construct andfunction as the computing system of FIG. 9, except that the main memory162 is coupled to the memory controller 134 via the main memoryinterface 192, which is coupled to the DS processing module 150. Assuch, the DS processing module processes instructions and/or datawritten to, or read from the main memory 162. As such, the instructionsand/or data stored in the main memory are done so in an error encodedmanner (i.e., as EC data slices). When a processing module requests aninstruction or data from the main memory via the memory controller, theDS processing module 150 converts the EC data slices of the instructionor data into a raw format of the instruction or data. Similarly, whenthe processing module desires to store an instruction or data in themain memory, the DS processing module 150 converts it from the rawformat into the error-coded format.

FIG. 12 is a schematic block diagram of another embodiment of thecomputing core coupled to one or more non-core memories 164 and/or toone or more LAN/WAN memories 166. The computing core includes one ormore processing modules 156-158, main memory 162, a memory controller134, a video processing unit 160, a plurality of ROM, an TO controller172, and TO interface, 170, and a DS memory interface module 168. Thememory controller 134 includes a memory processor unit 136, aninstruction cache 138, a data cache 140, a memory interface 144, abuffer 142, an input/request unit 146, an output unit 148, multiplexers152-154, a main memory interface 192, and the DS processing module 150.

This embodiment of the computing system is similar in construct andfunction as the computing system of FIG. 9, except that the DSprocessing module 150 is coupled to the input multiplexer 152 and theoutput multiplexer 154. In this embodiment, instruction and data writtento and read from the main memory are done in a raw format andinstructions and data written to and read from the non-core memoryand/or the LAN/WAN memory is done in an error-coded format. As such,instructions and/or data retrieved from the non-core memory and/or theLAN/WAN memory is decoded into the raw format prior to processing by theother elements of the memory controller. In addition, instructionsand/or data to be written to the non-core memory and/or the LAN/WANmemory is encoded into EC data slices by the DS processing module afterthe other elements of the memory controller have done their respectiveprocessing.

FIG. 13 is a schematic block diagram of another embodiment of acomputing core including the processing module 194, the video processingunit 196, the memory controller 198, the main memory 200, the IOcontroller 202, the IO interface 204, the peripheral component 206, theplurality of ROMs, the PCI interface 208, a NAND Flash 210, a hard drive212, and the LAN and/or WAN DSN memory 214. The video processing unit196 may include a frame buffer 216 to temporarily store raw data formatvideo data that may be transferred to a video display peripheralcomponent. The processing module 194 may include registers 218, a L1cache 220, and a L2 cache 222 for temporarily storing raw data formatinstructions or operational data.

The memory controller 198 perform memory mapping, EC data encoding, ECdata decoding, EC data slice routing, EC data slice retrieval, EC dataslice storage, raw data retrieval, and/or raw data storage. In thiscapacity, the memory controller 198 determines the file type format(e.g., raw data or EC data slices) to utilize when storing the dataobject. The determination may be based on one or more of apredetermination, a resiliency goal, a performance goal, a data objecttype, a user affiliation, and/or any other factor to improve theefficiency and/or performance of the computing core. For example, speedof access may be the most important factor when storing a raw formatapplication in main memory to be presently executed by the processingmodule 194. In another example, the resiliency of never losing thecompleted results data of an application may be more important than anyother factor when storing EC data slices format completed results datain the WAN DSN memory 214.

The memory controller 198 coordinates the storage, reading, and routingdata in a raw format and/or in an error-coded format (e.g., EC dataslices). For example, data (e.g., one or more of OS instructions,application instructions, active application configuration data, activeapplication results data, and/or any other data files required for fastcomputing core operation) conveyed between the memory controller and themain memory 200 may be in the raw format and/or in the error-codedformat. As another example, data conveyed between the memory controllerand the processing module 194 is the raw format. As yet another example,data conveyed between the memory controller and the video processingunit 196 is the raw format.

BIOS data conveyed between the memory controller 198 and the pluralityof ROM is done in the error-coded format. Data conveyed between thememory controller and the non-core memory of the NAND flash 210, thehard drive 212, and/or the LAN/WAN memory 214 may in the raw formatand/or the error-coded format. Similarly, data conveyed between thememory controller and a peripheral component may be in the raw format orin the error-coded format.

FIG. 14 is a logic diagram of another embodiment of a method for datahandling where the memory controller transfers data from one memory toanother. The memory controller receives a retrieve and/or store requestfrom the processing module 224. The memory controller determines asource location, memory type, and format based on vault parameters andthe DSN data to physical memory lookup table 226. For example, thesource location may be addresses within one or more types of memoryincluding the main memory, the NAND flash, the hard drive, the LAN DSNmemory, and/or the DSN WAN memory. The format may be raw or EC dataslices with a set of error control parameters (e.g., error codingalgorithm, number of pillars, segment size) 228. The memory controllerretrieves the raw format file or data object when the format is raw 230.

The memory controller retrieves the EC data slices when the format is ECdata slices 232 and decodes the EC data slices into the raw format dataobject based on the format 234 and save the raw file or data object inthe buffer 236. The memory controller determines a destination location,memory type, and format based on vault parameters and the DSN data tophysical memory lookup table 238. The location, memory type, and formatmay be different than the source location, memory type, and format torealize a different set of resiliency and performance characteristics240. For example, a dormant file that is in WAN memory may be errorcoded and dispersed to provide good protection. The dormant file may berequired to operate in main memory with more speed of successive accesssteps. The memory controller then retrieves the raw format file or dataobject when the destination file format is raw 242 and stores it in thedestination location 244.

The memory controller encodes the raw format data object in the bufferas EC data slices when the destination format is EC data slices 246. Thememory controller disperses the EC data slices by storing the EC dataslices in the memory devices based on the destination location and theDSN data to physical memory lookup table 248.

FIG. 15 is a schematic block diagram of another embodiment of a memorymapping including a ROM memory map, a hard drive (HD)/flash memory map,and a main memory map. The ROM memory map includes BIOS, power on selftest (POST) code, and a boot loader. The HD/flash memory map includesuser space and OS space. The main memory includes OS space and userspace. The memory maps indicate a typical boot process where BIOSexecutable instructions invoke transfer of the OS to the OS space inmain memory.

The processing module requests a boot address in ROM upon startup (e.g.,address FFFF). The processing module directly executes BIOS and POSTinstructions from the ROM which includes testing the computing corehardware and initializing elements that may require an initializationsequence (e.g., the video processing unit). The processing moduledetermines where the boot OS is located in the HD/flash memory map basedon the BIOS instructions. The processing module then executes the bootOS instructions to load the OS from the OS space of the HD/flash memoryinto the OS space of the main memory. Once the OS instructions areloaded, the processing module executes them.

FIG. 16 is a schematic block diagram of another embodiment of a memorymapping including a ROM memory map, a DSN LAN/WAN memory map, a GUIfunction, and a main memory map. The ROM memory map includes BIOS, poweron self test (POST) code, and an open GUI boot loader. The DSN LAN/WANmemory map includes user space and OS space. The main memory includes OSspace and user space. The memory maps indicate a boot process where BIOSexecutable instructions are decoded from EC data slices and executed toinvoke retrieval and decoding of OS EC data slices, which aretransferred to the OS space in main memory.

The processing module requests a boot address upon startup (e.g.,address FFFF). The memory controller retrieves BIOS instructions and theopen GUI boot loader instructions, both of which may be stored as ECdata slices in the DSN memory (e.g., BIOS ROM, non-core memory, harddrive, LAN/WAN memory). The memory controller decodes the EC data slicesand stores the decoded instructions in the OS section of main memory orin the memory controller. The processing module executes theinstructions to test the computing core, initialize the elementsrequiring initialization, and the processing module may determine whichuser is powering up the computing core by requesting a login via theopen GUI boot loader instructions. The processing module may determinean OS variant based on the login and vault for this user. The memorycontroller retrieves the EC data slices for the OS variant from the OSspace of the DSN memory. The memory controller decodes the EC dataslices to produce the OS variant in raw format. The memory controllercompletes the BIOS and POST instructions followed by transferring the OSvariant to the OS space within the main memory. The memory controllerfetches OS instructions for execution by the processing module.

In an example of operation, the processing module detects a boot-up ofthe computing device. The detection may be based on a power up sequencethat directs the processing module to fetch a predetermined address(e.g., such as $FFFF for a 16 bit address of a computing device). Theprocessing module addresses, via the memory controller, a distributedbasic input/output system (BIOS) memory to retrieve a plurality of errorcoded BIOS data slices. The distributed BIOS memory may include aplurality of memories and/or a plurality of read-only memories (ROM)that function. The plurality of memories and/or the plurality ofread-only memories (ROM) may include one or more of but not limited to aplurality of ROM memory devices for inclusion in a computing core, aplurality of local area network (LAN) memory devices, and/or a pluralityof wide area network (WAN) memory devices. A memory of the plurality ofmemories and/or the plurality of read-only memories (ROM) may includeone or more of but not limited to a read only memory (ROM) device, anerasable programmable read only memory (EPROM) device, an electronicallyerasable programmable read only memory (EEPROM) device, a nonvolatilerandom access memory (NVRAM), a flash memory device, a compact disc readonly memory (CD-ROM) device, and/or a digital video disc read onlymemory (DVD-ROM) device. The plurality of memories and/or read-onlymemories may operably couple to the memory controller via at least oneof an input output (10) controller and/or an input output (10)interface.

In the example of operation, the processing module executes a graphicaluser interface (GUI) function of a GUI boot loader to receive accountinformation. The account information may include one or more of but notlimited to a user identifier (ID), a vault identifier (ID), a password,and/or a password hash. The processing module determines the addressingof the distributed BIOS memory based on the account information. Forexample, the processing module determines the address of the distributedBIOS memory based on a table lookup for the user ID and vault ID. Thedistributed BIOS memory may include one or more of but not limited to alocal memory address, a local area network (LAN) memory address, and/ora wide area network (WAN) memory address.

In the example of operation, the processing module reconstructs BIOSdata from the plurality of error coded BIOS data slices using an errorcoding dispersal function and may store the plurality of error codedBIOS data slices in the main memory. The error coded dispersal functionincludes one or more of but not limited to a forward error correctionfunction, an information dispersal algorithm (IDA), turbo coding,convolutional coding, trellis coding, and/or Reed-Solomon coding.

In the example of operation, the processing module boots of thecomputing device in accordance with the BIOS data by generating andexecuting BIOS instructions based on the BIOS data. The BIOSinstructions may include one or more of but not limited to computingdevice initialization instructions, computing device test instructions,and/or operating system (OS) boot-up instructions. In an instance ofgenerating OS boot-up instructions, the processing module may identifyan OS, addresses a distributed OS memory to retrieve a plurality oferror coded OS data slices, and reconstruct an OS data segment from theplurality of error coded OS data slices using a second error codingdispersal function.

In another instance of generating OS boot-up instructions, theprocessing module may identify the OS, address the distributed OS memoryto retrieve a first plurality of error coded OS data slices, andreconstruct a first OS data segment from the first plurality of errorcoded OS data slices using the second error coding dispersal function.In the next step of the instance, the processing module determineswhether to retrieve a second plurality of error coded OS data slices.The processing module addresses the distributed OS memory to retrievethe second plurality of error coded OS data slices and reconstructs asecond OS data segment from the second plurality of error coded OS dataslices using the second error coding dispersal function when theprocessing module determines that the second plurality of error coded OSdata slices is to be retrieved.

FIG. 17 is a logic diagram of an embodiment of a method that begins withthe memory controller scanning the BIOS EC data slices from time to timeto determine if there are missing or corrupted slices 250. Thedetermination of corrupted EC data slices may be based on calculating aCRC for the present EC data slice and comparing the calculated CRC to astored CRC. The determination of missing EC data slices may be based onverifying that each slice is present as listed for the BIOS EC dataslices in the slice name to physical DSN memory address table. Forexample, the memory controller may determine where each slice is storedin the plurality of ROM DSN memories followed by a retrieval to verifyhow many slices are still present for each data segment of the BIOS dataobject.

The memory controller accesses the user vault to determine the errorcontrol parameters including the read threshold, a write threshold, andthe pillar width. The read threshold is the minimum number of recoveredslices required to decode the data segment and rebuild any slice. Thewrite threshold is the minimum number of good slices left after whichthe memory controller may rebuild all of the slices to the full pillarwidth. For example, if the write threshold is seven and seven goodslices still exist out of eight original slices (e.g., width=8), then noaction may be taken. In another example, if the write threshold is sevenand six good slices still exist out of eight original slices (e.g.,width=8), then the two missing slices may be rebuilt and re-stored in asuitable memory (e.g., not a ROM since it is read only but non-corememory or other).

The memory controller compares the number of good slices for a datasegment to the read threshold 252. The memory controller may generate analert that the BIOS has completely failed if the number of good slicesis less than the read threshold 254. The memory controller may not beable to rebuild the BIOS data object from the remaining good slices 260(e.g., from the ROM stored location). The computing core responds to thefailure alert by not allowing the computing core to restart by choiceuntil a substitute BIOS is arranged. The memory controller arranges fora substitute BIOS by accessing DSN WAN memory to find a suitable up todate BIOS.

The memory controller may compare the number of good slices for a datasegment to the write threshold when the number of good slices is notless than the read threshold 256. The memory controller may generate analert that the BIOS is below minimum if the number of good slices isless than the write threshold 258. The memory controller is able torebuild the BIOS data object from the remaining good slices (e.g., fromthe ROM stored location) and stores the rebuilt BIOS in a suitable DSNmemory 260. The computing core may respond to the failure alert byrecommending that the computing core not restart by choice until asubstitute BIOS is arranged.

The memory controller compares the number of good slices for a datasegment to the pillar width when the number of good slices is not lessthan the write threshold 262. The memory controller generates an alertthat the BIOS is above minimum, but less than the width if the number ofgood slices is not equal to the pillar width 264. The memory controlleris able to recover the BIOS data object from the remaining good slices(e.g., from the ROM stored location) upon restart. The computing coremay respond to the failure alert by recommending that the computing corenot restart by choice until a substitute BIOS is arranged.

In another example of operation, the memory controller determineswhether a BIOS data slice of a plurality of error coded BIOS data sliceshas a slice error. The memory controller reconstructs BIOS data fromother BIOS data slices of the plurality of error coded BIOS data slicesusing an error coding dispersal function (e.g., de-slice and decode) toproduce reconstructed BIOS data when the memory controller determinesthat the BIOS data slice has the slice error. The memory controllerrebuilds the plurality of error coded BIOS data slices from thereconstructed BIOS data to produce a rebuilt plurality of error codedBIOS data slices (e.g., encode and slice). The memory controllerfacilitates storage of the rebuilt plurality of error coded BIOS dataslices. For example, the memory controller may store the rebuiltplurality of error coded BIOS data slices in a non-volatile main memory.

FIG. 18 is a schematic block diagram of another embodiment of a memorymapping including the hard drive (HD)/flash memory map, and the mainmemory map. The HD/flash memory map may include user space and OS space.The HD/flash memory user space may include stored applications. The mainmemory may include OS space and user space. The memory map may indicatea typical sequence where an application is transferred from the HD/flashmemory user space to the main memory user space for execution by theprocessing module.

The processing module executes OS instructions from the main memory OSspace to invoke an application. The processing module determines wherethe application is located in the HD/flash memory map based on a tablelookup of application to physical storage location. The processingmodule executes OS instructions to load the application from the userspace of the HD/flash memory into the user space of the main memory. Theapplication may include application executable instructions,configuration parameters, and user preferences. The processing moduleexecutes instructions from the OS to initialize the application in mainmemory, which may include allocating working memory in the main memoryuser space. The processing module executes application executableinstructions under control of an OS task manager.

FIG. 19 is a schematic block diagram of another embodiment of a memorymapping including the DSN memory map, and the main memory map. The DSNmemory map may include user space and OS space across physical memoriesincluding one or more of HD/flash memory, DSN LAN memory, and DSN WANmemory. The main memory may include OS space and user space. The memorymaps may indicate an application activation process where EC data slicescontaining application executable instructions, configurationparameters, and user preferences may be retrieved from the DSN memory,decoded into raw data, and utilized.

The processing module executes OS instructions to invoke the applicationby requesting the memory controller fetch the application from DSNmemory. The memory controller accesses the DSN data to physical memorylookup table to determine where the application EC data slices arestored. In an example, the EC data slices are dispersed in the DSN LANmemory. In another example, the EC data slices are dispersed in the DSNWAN memory. In another example, the EC data slices are dispersed acrossboth the DSN LAN and DSN WAN memories. In another example, the EC dataslices are dispersed across the HD/flash memory, the DSN LAN memory andthe DSN WAN memory.

In an example, the read width number of EC data slice pillars per datasegment are stored in a portion of the DSN memory with a preferredperformance metric (e.g., low access latency) while the remainingpillars are stored in another portion of the DSN memory. For instance,six pillars may be stored in three memories of the DSN LAN memory andtwo pillars may be stored in two DSN WAN memories if the pillar width iseight and the read threshold is six. In this instance, a failure of anyone of the three DSN LAN memories can be overcome by accessing the twoDSN WAN memories in addition to the two remaining DSN LAN memories. Thememory controller may fetch the application in the quickest amount oftime from the three DSN LAN memories when there are no failed memories.

The memory controller fetches the application EC data slices from theminimum number of pillars (e.g., read threshold) with the preferredperformance metric by requesting the memory controller fetch theapplication from DSN memory. The memory controller fetches additionalpillars of EC data slices from the pillars with the next best preferredperformance metric when one or more of the pillars with the preferredperformance metric are unavailable or do not produce the requested ECdata slices.

The memory controller decodes the application EC data slices to producethe application in the raw data format and stores the raw data formatapplication in main memory or the memory controller may store the rawdata format application in a portion of the main memory and a portion ofDSN memory. The memory controller fetches the application initializationinstructions and executes them to establish the working memory in mainmemory and/or in the DSN memory. Next, the memory controller fetches theapplication instructions and the processing module executes them.

The memory controller saves the application configuration parameters anduser preferences in the DSN memory when the processing module initiatesan application shut down set of instructions. The memory controllerdetermines the portion of the DSN memory to utilize to save theapplication configuration parameters and the user preferences based onone or more of an activity metric (e.g., how frequent is thisapplication activated), a predetermination, a user lookup table, anapplication lookup table, and/or the current performance metric of theDSN memory.

In an example of operation, the processing module and/or memorycontroller may perform the steps of a method to load an application forexecution based on retrieving EC data slices and reconstructinginstructions on the application as described below. The processingmodule detects selection of an application. For example, the processingmodule receives an application selection message. The at least one ofthe memory controller and/or the processing module addresses adistributed application memory to retrieve a plurality of error codedprogram data slices and a plurality of error coded configuration dataslices. In an embodiment, the at least one of the memory controllerand/or the processing module addresses a first memory of the distributedapplication memory to retrieve the plurality of error coded program dataslices and addresses a second memory of the distributed applicationmemory to retrieve the plurality of error coded configuration dataslices. The at least one of the memory controller and/or the processingmodule addresses the distributed application memory by one or more ofaddressing at least one of a plurality of local non-volatile memorydevices, addressing at least one of a plurality of LAN memory devicesand/or addressing at least one of a plurality of WAN memory devices.

In the next step of the example, the at least one of the memorycontroller and/or the processing module reconstructs a data segment of aprogram from the plurality of error coded program data slices using anerror coding dispersal function and the at least one of the memorycontroller and/or the processing module reconstructs a data segment ofconfiguration information from the plurality of error codedconfiguration data slices using a second error coding dispersal functionwherein the second error coding dispersal function is substantially thesame as the error coding dispersal function. In another instance, thesecond error coding dispersal function is not substantially the same asthe error coding dispersal function. At least one of the memorycontroller and/or the processing module stores the data segment of theprogram and the data segment of the configuration information in themain memory.

In another example, the at least one of the memory controller and/or theprocessing module detects a change in configuration information. Forexample, the computing core may change the configuration informationwhen the computing core receives a preference change message. The atleast one of the memory controller and/or the processing module updatesthe configuration information to produce updated configurationinformation and facilitates storage of the updated configurationinformation when the at least one of the memory controller and/or theprocessing module detects the change in configuration information. Theat least one of the memory controller and/or the processing module mayfacilitate storage of the updated configuration information by encodingand slicing the updated configuration information in accordance with thesecond error coding dispersal function to produce a new plurality oferror coded configuration data slices. The at least one of the memorycontroller and/or the processing module addresses the distributedapplication memory and/or main memory to store the new plurality oferror coded configuration data slices. In an embodiment, the at leastone of the memory controller and/or the processing module may addressthe main memory to store the updated configuration information.

In an example of operation, the processing module and/or memorycontroller may perform the steps of a method to close an application asdescribed below. The processing module detects closing of anapplication. For example, the processing module receives an applicationclose message. The at least one of the memory controller and/or theprocessing module reads a data segment of configuration information ofthe application from the main memory. The at least one of the memorycontroller and/or the processing module generates a plurality of errorcoded configuration data slices using a second error coding dispersalfunction from the data segment and the at least one of the memorycontroller and/or the processing module addresses a distributedapplication memory for storage of the plurality of error codedconfiguration data slices when enabled. For instance, the functiondescribed above may always be enabled. In another instance, the functiondescribed above may only be enabled when the at least one of the memorycontroller and/or the processing module determines that theconfiguration information has changed. The at least one of the memorycontroller and/or the processing module addresses the distributedapplication memory by one or more of addressing at least one of aplurality of local non-volatile memory devices, addressing at least oneof a plurality of LAN memory devices, and/or addressing at least one ofa plurality of WAN memory devices.

FIG. 20 is a schematic block diagram of an embodiment of a memory systemthat includes a plurality of M+1 memory layers each with one or morememory modules operably coupled by a network. The memory modules of thememory layer may share similar layer attributes including one or more ofresiliency, cost, access latency, capacity and/or other factors thatdescribe efficiency, effectiveness, and performance. For example, memorymodules of layer 0 may have the lowest access latency and highestnormalized cost of all the layers while the memory modules of layer Mmay have the lowest normalized cost and highest latency of all thelayers. The memory module may be included in the user device, the memorysystem, the database, the server, the router, and/or the modem. A morespecific example of the memory system will be discussed in greaterdetail with reference to FIG. 21.

The memory module may include a memory, the memory controller, and theinterface to the other memory modules via the network. The memory mayinclude one or more memory elements of the hard drive, the NAND flash,the ROM, the main memory, the RAM memory, the non-core memory, and anoptical drive. The memory modules of the same memory layer may sharesimilar memory elements thus producing similar layer attributes. Theinterface may provide an electrical, wireless, and/or optical connectionbetween the memory module and the network. The network may include oneor more of a computing core backplane, the LAN, the WAN, and/or anyother wire line and/or wireless communications.

The memory controller may include the dispersed storage (DS) processingmodule and may function to coordinate the reading of data and writing ofdata, including data which is stored in the memory of memory modules.For example, the memory controller may create and disperse EC data slicepillars of a data object across layer 0 memory modules. In anotherexample, the memory controller may transfer EC data slices from thelayer 2 memory modules to the layer 1 memory modules without decoding orre-encoding EC data slices. In another example, the memory controllermay retrieve EC data slices from the layer 3 memory modules and decodethe EC data slices to produce the raw data object.

The memory controller may re-encode the raw data object into EC dataslices of a different error control parameter set and store the EC dataslices in layer 1 memory modules. The error control parameter set mayinclude the pillar width, the write threshold, the read threshold, thecoding scheme, the pre-data manipulation parameters, the post-datamanipulation parameters, and/or other parameters to specify how EC dataslice are constructed. For example, the memory controller may utilize afirst set of error control parameters at layer 0 including the pillarwidth four and the read threshold three, and the memory controller mayutilize a second set of error control parameters at layer 3 includingthe pillar width sixteen and the read threshold ten. The memorycontroller may match the error control parameters to the layerattributes to optimize effectiveness and performance. For example, thememory controller in memory module 0_0 may utilize main memory in thememory of memory modules 0_0 and 0_1 as memory layer 0 and it mayutilize a hard drive set in the memory of memory modules 2_0 and 2_1 asmemory layer 2 via the network.

The memory layer reference and utilization may be with reference to aparticular memory module position and relationship (e.g., proximity viathe network) to the other memory modules. For example, the memorycontroller in memory module 1_0 may utilize main memory in the memory ofmemory modules 1_0 and 1_1 as memory layer 0 and it may utilize a harddrive set in the memory of memory modules 3_0 and 3_1 as memory layer 2via the network.

The memory controller may store the same data object with the same ordifferent error control parameters at two or more memory layers inaccordance with a duplication parameter. The duplication parameter mayspecify that the data object be converted into one, two, or more sets ofEC data slices where each set may have a different error controlparameter set and that the EC data slices be stored in one, two, or morememory layers to provide another measure of resiliency. For example, thememory controller may initiate a storage sequence by determining theduplication parameter where the determination is based on a vault tablelookup, the data object type, a user identifier, a resiliency indicator,and/or a prioritization indicator. The memory controller may produce afirst set of EC data slices utilizing a first set of error controlparameters (e.g., pillar width 4, read threshold 3) and a second(duplicate) set of EC data slices utilizing a second set of errorcontrol parameters (e.g., pillar width 8, read threshold 6). The memorycontroller may store the first set of EC data slices in memory layer 1memory modules 1_0 and 1_1 and the memory controller may store thesecond (duplicate) set of EC data slices in memory layer 3 memorymodules 3_0 and 3_1.

FIG. 21 is a schematic block diagram of another embodiment of a memorysystem that includes a plurality of user devices and a plurality ofmemory systems mapped to memory layers 0-3 each with one or morememories operably coupled by a network. The layer 0 and 1 user devicemay include a computing core and one or more non-core memories. Thecomputing core may include the core memory at layer 0, the memorycontroller, and the interface to the network. The layer 2 and layer 3user devices and layer 2 and layer 3 memory systems may include thememory operably coupled to the network via the interface. Memories ofthe each memory layer may share similar layer attributes including oneor more of resiliency, cost, access latency, capacity and/or otherfactors that describe efficiency, effectiveness, and performance. Forexample, memory of layer 0 may have the lowest access latency andhighest normalized cost of all the layers while the memory of layer 3may have the lowest normalized cost and highest latency of all thelayers. The memory may be included in the user device, the memorysystem, the database, the server, the router, and/or the modem.

The memory may include one or more memory elements of the hard drive,the NAND flash, the ROM, the main memory, the RAM memory, the non-corememory, and an optical drive. The memory modules of the same memorylayer may share similar memory elements thus producing similar layerattributes. The interface may provide an electrical, wireless, and/oroptical connection between the memory module and the network. Thenetwork may include one or more of a computing core backplane, the LAN,the WAN, and/or any other wire line and/or wireless communications.

The memory controller may include the dispersed storage (DS) processingmodule and may function to coordinate the reading of data and writing ofdata, including data which is stored in the memory of memory layers. Forexample, the memory controller may create and disperse EC data slicepillars of a data object across layer 0 core memory. In another example,the memory controller may transfer EC data slices from the layer 2memory in the memory systems to the layer 1 non-core memory withoutdecoding or re-encoding EC data slices. In another example, the memorycontroller may retrieve EC data slices from the layer 3 memory in theuser devices and memory systems and decode the EC data slices to producethe raw data object for use by the computing core and/or to be stored inanother layer.

Successive layers of memory may provide more data storage resiliency.The memory controller may utilize the non-core memory of layer 1 toovercome storage failure issues (e.g., core memory device failures) atlayer 0. The memory controller may utilize the user device and memorysystem memory of layer 2 via the LAN (e.g., same site as the userdevice) to overcome storage failure issues (e.g., user device failure)at layers 0-1. The memory controller may utilize the user device andmemory system memory of layer 3 via the WAN (e.g., different sites fromthe user device) to overcome storage failure issues (e.g., site failure)at layers 0-2.

The memory controller may re-encode the raw data object into EC dataslices of a different error control parameter set and store the EC dataslices in layer 1 non-core memory. The error control parameter set mayinclude the pillar width, the write threshold, the read threshold, thecoding scheme, the pre-data manipulation parameters, the post-datamanipulation parameters, and/or other parameters to specify how EC dataslice are constructed. For example, the memory controller may utilize afirst set of error control parameters at layer 0 including the pillarwidth four and the read threshold three, and the memory controller mayutilize a second set of error control parameters at layer 3 includingthe pillar width sixteen and the read threshold ten. The memorycontroller may match the error control parameters to the layerattributes to optimize effectiveness and performance. For example, thememory controller may utilize core memory in the computing core asmemory layer 0 and it may utilize a hard drive set in the layer 2non-core memory of the user device.

The memory controller may store the same data object with the same ordifferent error control parameters at two or more memory layers inaccordance with a duplication parameter. The duplication parameter mayspecify that the data object be converted into one, two, or more sets ofEC data slices where each set may have a different error controlparameter set and that the EC data slices be stored in one, two, or morememory layers to provide another measure of resiliency. For example, thememory controller may initiate a storage sequence by determining theduplication parameter where the determination is based on a vault tablelookup, the data object type, a user identifier, a resiliency indicator,and/or a prioritization indicator. The memory controller may produce afirst set of EC data slices utilizing a first set of error controlparameters (e.g., pillar width 4, read threshold 3) and a second(duplicate) set of EC data slices utilizing a second set of errorcontrol parameters (e.g., pillar width 8, read threshold 6). The memorycontroller may store the first set of EC data slices in layer 1 non-corememory and the memory controller may store the second (duplicate) set ofEC data slices in layer 3 memory. The method to duplicate data objectsin the DSN memory in accordance with data object usage state will bediscussed in greater detail with reference to FIGS. 22-23.

FIG. 22 is a state diagram of an example embodiment of a memory systemthat includes three states of data object usage that may be utilized bythe memory controller to optimize the DSN memory system for a desiredbalance of resiliency and performance. In an example, the memorycontroller may determine the balance to favor more resiliency at thecompromise of slower performance. In another example, the memorycontroller may determine the balance to favor faster performance at thecompromise of less resiliency.

The memory controller may provide the level of resiliency based onutilization of one or more memory layers where different error controlparameters are utilized at different levels. The memory controller mayprovide the level of resiliency based on duplication where data objectsstored at a first memory layer are duplicated at a second or more memorylayer.

The memory controller may determine the level of resiliency based on ausage characteristic and/or the state of usage of the data object. Thememory controller may determine the data object usage characteristicbased on one or more of an average frequency of retrieval rate, anaverage duration of use, and an average frequency of storage rate. Thememory controller may determine the state of usage (e.g., dormant,active, recently active) based on the instantaneous computing core usageof the data object and a timing parameter denoting the time since thelast state transition.

In an example of operation that may favor speed, the data object residesin layer 3 memory as the current version in the dormant state. Thememory controller may retrieve the data object EC data slices from thelayer 3 memory when the memory controller receives an open file requestfrom the computing core when the state is dormant. The memory controllerchanges the state to active and decodes the EC data slices into rawdata. The memory controller stores the raw data in layer 0 memory as atemporary version for utilization and potential modification by thecomputing core. The memory controller encodes the raw data into EC dataslices and disperses the EC data slices to memory layer 1 as the currentversion data object. The memory controller deletes the data object ECdata slices at layer 3.

The memory controller encodes the raw format temporary version of thedata object from layer 0 into EC data slices and disperses the EC dataslices to memory layer 2 as the temporary version data object when thememory controller receives a close file command. The memory controllerdeletes the data object EC data slices at layers 0 and 1. The memorycontroller starts a timeout timer (e.g., a timer that starts at 1 minuteand counts down). The memory controller may determine the timeout timerduration based on of one or more of a predetermination, an averagefrequency of retrieval rate, an average duration of use, an averagefrequency of storage rate, and an average time duration betweensubsequent file opens. The memory controller changes the state torecently active.

The memory controller may retrieve the data object temporary version ECdata slices from the layer 2 memory when the memory controller receivesan open file request from the computing core when the state is recentlyactive and the timeout timer has not expired. The memory controllerchanges the state to active and decodes the EC data slices into rawdata. The memory controller stores the raw data in layer 0 memory as atemporary version for utilization and potential modification by thecomputing core. The memory controller encodes the raw data into EC dataslices and disperses the EC data slices to memory layer 1 as the currentversion data object. The memory controller deletes the data object ECdata slices at layer 2.

The memory controller retrieves the EC data slices from memory 2 of thetemporary version data object, decodes the EC data slices into the rawformat and encodes the raw format temporary version of the data objectinto EC data slices and disperses the EC data slices to memory layer 3as the current version data object when the memory controller detectsthe timeout timer expiration and the state is recently active. Thememory controller deletes the data object EC data slices at layer 2. Thememory controller changes the state to dormant.

FIG. 23 is a state diagram of another example embodiment of a memorysystem that includes three states of data object usage that may beutilized by the memory controller to optimize the DSN memory system fora desired balance of resiliency and performance. In an example, thememory controller may determine the balance to favor more resiliency atthe compromise of slower performance. In another example, the memorycontroller may determine the balance to favor faster performance at thecompromise of less resiliency.

The memory controller may provide the level of resiliency based onutilization of one or more memory layers where different error controlparameters are utilized at different levels. The memory controller mayprovide the level of resiliency based on duplication where data objectsstored at a first memory layer are duplicated at a second or more memorylayer.

The memory controller may determine the level of resiliency based on ausage characteristic and/or the state of usage of the data object. Thememory controller may determine the data object usage characteristicbased on one or more of an average frequency of retrieval rate, anaverage duration of use, and an average frequency of storage rate. Thememory controller may determine the state of usage (e.g., dormant,active, recently active) based on the instantaneous computing core usageof the data object and a timing parameter denoting the time since thelast state transition.

In an example of operation that may favor resiliency, the data objectresides in layers 2 and 3 memory as the current version in the dormantstate. The memory controller may retrieve the data object EC data slicesfrom the layer 2 memory (or layer 3 memory if layer 2 has failed) whenthe memory controller receives an open file request from the computingcore when the state is dormant. The memory controller changes the stateto active and decodes the EC data slices into raw data. The memorycontroller stores the raw data in layer 0 memory as a temporary versionfor utilization and potential modification by the computing core. Thememory controller encodes the raw data into two sets of EC data slicesand disperses the EC data slices to memory layer 1 and 2 as thetemporary version data object. Note that the EC data slices at layer 3are not deleted.

The memory controller encodes the raw format temporary version (newestversion) of the data object from layer 0 into two sets of EC data slicesand disperses the EC data slice sets to memory layers 1 and 2 as thetemporary version data object when the memory controller receives aclose file command and the state is active. The memory controllerdeletes the data object EC data slices at layer 0. The memory controllerstarts a timeout timer (e.g., a timer that starts at 1 minute and countsdown). The memory controller may determine the timeout timer durationbased on of one or more of a predetermination, an average frequency ofretrieval rate, an average duration of use, an average frequency ofstorage rate, and an average time duration between subsequent fileopens. The memory controller changes the state to recently active. Notethat the EC data slices at layer 3 are not deleted and remain as the oldversion of the data object.

The memory controller may retrieve the data object temporary version ECdata slices from the layer 2 memory (or layer 1 if layer 2 fails) whenthe memory controller receives an open file request from the computingcore when the state is recently active and the timeout timer has notexpired. The memory controller changes the state to active and decodesthe EC data slices into raw data. The memory controller stores the rawdata in layer 0 memory as a temporary version for utilization andpotential modification by the computing core. The memory controllerencodes the raw data into EC data slices and disperses the EC dataslices to memory layers 1 and 2 as the temporary version data object.

The memory controller retrieves the EC data slices from memory layer 1(or layer 2 if layer 1 fails) of the temporary version data object, anddecodes the EC data slices into the raw format and encodes the rawformat temporary version of the data object into two sets of EC dataslices and disperses the EC data slices to memory layers 2 and 3 as thecurrent version data object when the memory controller detects thetimeout timer expiration and the state is recently active. The memorycontroller deletes the data object EC data slices at layer 1. The memorycontroller changes the state to dormant.

FIG. 24 is a schematic block diagram of another embodiment of a memorymapping including the memory controller cache, the DSN memory map, andthe main memory map. The DSN memory map may include user space and OSspace across physical memories including one or more of HD/flash memory,DSN LAN memory, and DSN WAN memory. The main memory may include OS spaceand user space. The memory maps may indicate an application versionupdate and activation process where a new application version may bereceived into the memory controller cache from an external entity (e.g.,an application server on the internet) and the memory controller maycreate and store EC data slices for the new application version in theDSN memory. The memory controller may subsequently retrieve the newapplication EC data slices from the DSN memory, decode the slices intoraw data, and provide the raw data format application to the computingcore for execution. The memory controller may save EC data slicescontaining application executable instructions, configurationparameters, and user preferences.

The processing module executes OS instructions to invoke the applicationby requesting the memory controller fetch the application from DSNmemory. The memory controller accesses the DSN data to physical memorylookup table to determine where the application EC data slices arestored. In an example, the EC data slices are dispersed in the DSN LANmemory. In another example, the EC data slices are dispersed in the DSNWAN memory. In another example, the EC data slices are dispersed acrossboth the DSN LAN and DSN WAN memories. In another example, the EC dataslices are dispersed across the HD/flash memory, the DSN LAN memory andthe DSN WAN memory.

In an embodiment, the read width number of EC data slice pillars perdata segment are stored in a portion of the DSN memory with a preferredperformance metric (e.g., low access latency) while the remainingpillars are stored in another portion of the DSN memory. For example,six pillars may be stored in three memories of the DSN LAN memory andtwo pillars may be stored in two DSN WAN memories if the pillar width iseight and the read threshold is six. In this instance, a failure of anyone of the three DSN LAN memories can be overcome by accessing the twoDSN WAN memories in addition to the two remaining DSN LAN memories. Thememory controller fetches the application in short amount of time fromthe three DSN LAN memories when there are no failed memories.

The memory controller fetches the application EC data slices from theminimum number of pillars (e.g., read threshold) with the preferredperformance metric by requesting the memory controller fetch theapplication from DSN memory. The memory controller fetches additionalpillars of EC data slices from the pillars with the next best preferredperformance metric when one or more of the pillars with the preferredperformance metric are unavailable or do not produce the requested ECdata slices.

The memory controller decodes the application EC data slices to producethe application in the raw data format. The memory controller determinesif the application version is current by requesting the latest versionnumber from one of the external entity or from a version table stored inthe DSN memory. The memory controller stores the raw data formatapplication in main memory or the memory controller may store the rawdata format application in a portion of the main memory and a portion ofDSN memory when the memory controller determines that the applicationversion from DSN memory is current.

The memory controller deletes the application EC data slices in the DSNmemory (e.g., executable code only, not the configuration parameters anduser preferences) and determines where to obtain the current applicationversion when the application version from DSN memory is not current. Thedetermination may be based on a DSN table entry and/or by requesting thecurrent version location from the external entity. The memory controllerrequests the new version and temporarily stores the current version inthe memory controller cache. The memory controller decodes the EC dataslices in the cache of the current application version into the rawformat when the current version application was obtained in EC dataslice format. The memory controller stores the raw format application inmain memory and encodes the raw format application into EC data slicesfor storage in the DSN memory. The memory controller stores the EC dataslices in the DSN memory.

The memory controller fetches the application initializationinstructions. The processing module executes the applicationinitialization instructions to establish the working memory in mainmemory and/or in the DSN memory. Once set up, the memory controllerfetches the application instructions and the processing module executesthe application instructions.

The memory controller saves the application configuration parameters,and user preferences in the DSN memory when the processing moduleinitiates an application shut down set of instructions. The memorycontroller determines the portion of the DSN memory to utilize to savethe application configuration parameters, and user preferences based onone or more of an activity metric (e.g., how frequent is thisapplication activated), a predetermination, a user lookup table, anapplication lookup table, and/or the current performance metric of theDSN memory.

FIG. 25 is a schematic block diagram of another embodiment of a memorysystem that includes a plurality of solid-state (SS) memory units 1-4,the DS processing module, and the interface. The SS memory units mayinclude ROM, RAM, NAND flash memory. In an example, inexpensive NANDflash (relative to other flash) is utilized to provide a more resilientmemory system (as compared to just a single inexpensive NAND flash)utilizing four pillars of EC data slices per data segment where the readthreshold is three pillars.

The interface provides an electrical and/or optical coupling to thememory system. In an embodiment, the interface may replicate theelectrical interface of a typical NAND flash. In another embodiment, thememory system may mimic a database system and may utilize a databaseaccess protocol to mimic a conventional file system interface and may beany one or more of network file system (NFS), flash file system (FFS),disk file system (DFS), small computer system interface (SCSI), internetsmall computer system interface (iSCSI), file transfer protocol (FTP),and web-based distributed authoring and versioning (WebDAV). In anotherembodiment, the database may utilize a dispersed storage network (DSN)protocol.

In an example of operation, the DS processing module may encode areceived data object via the interface to produce a set of four pillarEC data slices per segment. The DS processing module may disperse thefour pillar EC data slices amongst the four SS memory units 1-4 for allof the data segments of the data object.

In an embodiment, the DS processing module may rebuild corrupted ormissing EC data slices from time to time to maintain the integrity ofthe data. In an example, the DS processing module may scan the SS memoryunits 1-4 for corrupted or missing data slices. The DS processing modulemay determine corrupted EC data slices when a comparison of a calculatedCRC to a stored CRC does not match. The DS processing module maydetermine missing EC data slices when a comparison of entries in the DSNmemory to physical address table does not match the actual stored ECdata slices. The DS processing module may retrieve the good slicescorresponding to the missing or corrupted slice and decode the goodslices to produce the original raw data object. The DS processing modulemay encode the raw data object to produce reconstructed EC data slices.The DS processing module may store the reconstructed EC data slicecorresponding to the corrupted or missing EC data slice.

In another example of operation, the DS processing module may receive aretrieve request via the interface. The DS processing module maydetermine the locations of the EC data slices for the data object byaccessing the DSN memory to physical address table. The DS processingmodule may retrieve the minimum number (e.g., read threshold) of EC dataslices corresponding to the data object and may decode the EC dataslices to produce the original raw data object. The DS processing modulemay transmit the raw data object via the interface.

As may be used herein, the terms “substantially” and “approximately”provides an industry-accepted tolerance for its corresponding termand/or relativity between items. Such an industry-accepted toleranceranges from less than one percent to fifty percent and corresponds to,but is not limited to, component values, integrated circuit processvariations, temperature variations, rise and fall times, and/or thermalnoise. Such relativity between items ranges from a difference of a fewpercent to magnitude differences. As may also be used herein, theterm(s) “coupled to” and/or “coupling” and/or includes direct couplingbetween items and/or indirect coupling between items via an interveningitem (e.g., an item includes, but is not limited to, a component, anelement, a circuit, and/or a module) where, for indirect coupling, theintervening item does not modify the information of a signal but mayadjust its current level, voltage level, and/or power level. As mayfurther be used herein, inferred coupling (i.e., where one element iscoupled to another element by inference) includes direct and indirectcoupling between two items in the same manner as “coupled to”. As mayeven further be used herein, the term “operable to” indicates that anitem includes one or more of power connections, input(s), output(s),etc., to perform one or more its corresponding functions and may furtherinclude inferred coupling to one or more other items. As may stillfurther be used herein, the term “associated with”, includes directand/or indirect coupling of separate items and/or one item beingembedded within another item. As may be used herein, the term “comparesfavorably”, indicates that a comparison between two or more items,signals, etc., provides a desired relationship. For example, when thedesired relationship is that signal 1 has a greater magnitude thansignal 2, a favorable comparison may be achieved when the magnitude ofsignal 1 is greater than that of signal 2 or when the magnitude ofsignal 2 is less than that of signal 1.

The present invention has also been described above with the aid ofmethod steps illustrating the performance of specified functions andrelationships thereof. The boundaries and sequence of these functionalbuilding blocks and method steps have been arbitrarily defined hereinfor convenience of description. Alternate boundaries and sequences canbe defined so long as the specified functions and relationships areappropriately performed. Any such alternate boundaries or sequences arethus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid offunctional building blocks illustrating the performance of certainsignificant functions. The boundaries of these functional buildingblocks have been arbitrarily defined for convenience of description.Alternate boundaries could be defined as long as the certain significantfunctions are appropriately performed. Similarly, flow diagram blocksmay also have been arbitrarily defined herein to illustrate certainsignificant functionality. To the extent used, the flow diagram blockboundaries and sequence could have been defined otherwise and stillperform the certain significant functionality. Such alternatedefinitions of both functional building blocks and flow diagram blocksand sequences are thus within the scope and spirit of the claimedinvention. One of average skill in the art will also recognize that thefunctional building blocks, and other illustrative blocks, modules andcomponents herein, can be implemented as illustrated or by discretecomponents, application specific integrated circuits, processorsexecuting appropriate software and the like or any combination thereof.

What is claimed is:
 1. A computing core comprises: memory that ispartitioned into a user section and a kernel section, wherein the usersection is divided into a first set of pillars, wherein the kernelsection is divided into a second set of pillars; and a memory controlleroperably coupled to the memory, wherein the memory controller isoperably to: dispersed storage error encode a data segment of user datainto a set of encoded user data slices; store the set of encoded userdata slices in the first set of pillars of the user section; dispersedstorage error encode a data segment of system data into a set of encodedsystem data slices; and store the set of encoded system data slices inthe second set of pillars of the kernel section.
 2. The computing coreof claim 1, wherein the memory comprises one or more of: a main memory;and an interface coupling to one or more of a hard disk drive, anexternal FLASH memory, and an external dispersed storage network (DSN)memory.
 3. The computing core of claim 1, wherein the memory controlleris further operable to: retrieve a decode threshold number of encodeduser data slices of the set of encoded user data slices from the memory;dispersed storage error decode the decode threshold number of encodeduser data slices to recover the data segment of the user data; andprovide the recovered data segment to a processing module of thecomputing core.
 4. The computing core of claim 1, wherein the memorycontroller is further operable to: retrieve a decode threshold number ofencoded system data slices of the set of encoded system data slices fromthe memory; dispersed storage error decode the decode threshold numberof encoded system data slices to recover the data segment of the systemdata; and provide the recovered data segment to processing module of thecomputing core.
 5. The computing core of claim 1 further comprises: theuser section is logically divided into the first set of pillars; and thekernel section is logically divided into the second set of pillars. 6.The computing core of claim 1 further comprises: the user section isphysically divided into the first set of pillars; and the kernel sectionis physically divided into the second set of pillars.
 7. The computingcore of claim 1 further comprises: the system data including one or moreof: an operating system and an application program interface (API); andthe user data including one or more of: a user application and asoftware driver.